if the short name of button id 4 is "Action On" then click at 39,326
end closecard
on domenu which
if which is "New Card" or which is "Cut card" or which is "Delete Card" then
beep 3
exit domenu
end if
if which is "Protect Stack..." then
beep 3
answer "You don't want to do that!"
exit domenu
end if
if which is "Delete Stack..." then
play boing
answer "You really don't want to do that!"
exit domenu
end if
pass domenu
end domenu
-- part 3 (field)
-- low flags: 00
-- high flags: 0007
-- rect: left=84 top=27 right=342 bottom=510
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 0
-- font id: 3
-- text size: 9
-- style flags: 0
-- line height: 12
-- part name: The Facts
----- HyperTalk script -----
on mousewithin
if the OptionKey is down then
if the locktext of the target is true then
put true into DidUnlock
set locktext of target to false
else
put false into DidUnlock
end if
set the cursor to 2
repeat while (the OptionKey is down) and (item 1 of the rect of target <= item 1 of the mouseLoc) and (item 1 of the mouseLoc <= item 3 of the rect of target) and (item 2 of the rect of target <= item 2 of the mouseLoc) and (item 2 of the mouseLoc <= item 4 of the rect of target)
if the Mouse is down then
click at the MouseLoc
click at the ClickLoc
put selection into selectedWord
if field CrossRef contains selectedWord then
set visible of card field selectedWord to true
wait until the mouseclick is true
set visible of card field selectedWord to false
else
beep
answer "Do you see any asterisk there?!" with "Oooh"
exit mousewithin
end if
end if
end repeat
if DidUnlock then
set the locktext of the target to true
end if
end if
end mousewithin
-- part 1 (field)
-- low flags: 00
-- high flags: 0000
-- rect: left=1 top=4 right=317 bottom=82
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 0
-- font id: 3
-- text size: 9
-- style flags: 256
-- line height: 12
-- part name: Steve
-- part 2 (field)
-- low flags: 00
-- high flags: 0000
-- rect: left=188 top=5 right=22 bottom=429
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 3
-- text size: 12
-- style flags: 256
-- line height: 16
-- part name: Name
-- part 4 (button)
-- low flags: 00
-- high flags: A004
-- rect: left=4 top=318 right=339 bottom=77
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: Action Off
----- HyperTalk script -----
on mouseUp
if the optionkey is down then
pass mouseup
end if
if the short name of the target is "Action Off" then
Individual contributions are credited individually.
A continuing resource for Hypercard* developers.
•••Items with an asterisk (*) hold additional information. Hold down the
option key and click on the word to access this information•••
•It will be easier to read this card if you click on the 'Action Off' button•
The purpose of this stack:
This stack is designed for anyone developing Hypercard stacks. It includes public domain and shareware XFCNs*, XCMDs*, HyperTalk functions and useful script segments. It is a user supported effort and will constantly be growing. The basic idea is to collect all the useful resources* a Hypercard developer needs into one place, making the development process much easier and faster. This stack is designed as a learning tool. Nothing is protected or hidden from the user. Tear into the scripts until you understand what they do. Play around with the XCMDs and XFCNs.
How it works:
This copy of the stack you are reading is the main library* for all the information. It is being distributed through electronic bulletin boards, users groups, and other public domain sources. About every three* weeks it will be updated to include all the latest ideas & techniques that may be useful to a Hypercard developer.
Each update will be released in 2 formats. The first format will be the original Developer stack, which you are now looking at. The second format will be an updater* stack. Since the original library stack will begin to grow quite large, anyone who already has this stack (like you) can get just the updater stack. This method will make getting updates a lot less expensive for those people who download them from commercial bulletin boards.
You may add as many cards as you like to this stack without affecting the operation of the updater stacks. Just be certain not to rename or delete any of the backgrounds. For a larger distribution of ideas, it would be better if you send new script segments, functions, XFCNS, & XCMDs to us for inclusion in stack updates.
What you have to do:
The only way this stack will succeed as a useful resource for developers is if everyone contributes. It's easy to do, and you even get something in return. If you have written any XFCNs, XCMDs, functions, scripts, or other HyperCard related items that you have found useful, send it to us, on a disk, to the address below. In return, you will receive the latest version of the Developer Stack, and a warm feeling inside from being a contributing member of the Macintosh* and Hypercard community. Hypercard has made developers out of many people who would have never thought of programming before. Now the Developer Stack is here to make distribution of all the great new ideas and techniques simple.
Credits:
I have tried to give credit for everything included in the stack. There are a few items that have gone without credits because I don't know where they originally came from. If you recognize any of them, and can attribute them to the correct person, please let me know. Anything sent for inclusion in the stack, will be credited to the person who created it. (You too can become famous and people will be able to talk behind your back, if you would only contribute.)
My Committment:
January 24, 1987 Bellevue Hospital... Oh, not that kind of committment. Actually I am committed to bringing out updates of this stack about every three* weeks, as long as people contribute. With all the action going on in the Hypercard community we can all benefit from new ideas and resources*, collected into one place. This is just a small taste of what is to come in the updater stacks. I will take contributions from any source with the following conditions:
1) If you send something to be included in the stack, it should be debugged and ready to go.
If it includes any scripts, they should be well commented, and have a header giving credit to yourself. I will include shareware items in the stack, and make the appropriate notations.
2) If you send something to be included in the stack, and want to receive the latest version of the Developer Stack, you MUST include a self-addressed stamped envelope. If you don't, you won't get your disk back.
3) If you have any ideas or comments about the stack, and where it should go (future direction-wise, not physically), LET ME KNOW! Don't keep your ideas to yourself. I would like to see this grow into a useful tool for ALL Hypercard users, not just the experts. While this stack has been tested thoroughly, there still may be some bugs (did I here someone whisper MicroSoft Word 3.0?). If you find any PUHLEASE let me know. Send me mail (USPS or electronic).
4) I cannot guarantee that any specific contribution will be included in an update of the stack. However, any that are included will be given full credit as to their original source.
How to reach me:
(You gotta stand way up on your tippy toes...)
US MAIL:
Steve Drazga*
Box 388
Southampton, PA 18966
(215) 464-3733
or
ART Incorporated
315 North Washington Ave.
Moorestown, NJ 08057
(609) 778-3601
GEnie (I am on GEnie regularly):
S.DRAZGA
Compuserve (I am on CIS less frequently than GEnie):
76530,1107
What you should send as a contributor:
1) A disk with your contribution. Since it probably won't fill up the entire disk, you can also include some stacks, sounds (I love those digitized sounds), or any other neat programs you have.
2) A self-addressed stamped envelope - if you want your disk returned with a copy of the latest update of the Developer Stack.
3) A note telling me what Hypercard is in 15 words or less (HA!).
4) $100,000* in small bills, or your suggestions for the continuing growth of this stack as a developers' tool, if you happen to be low on cash.
What if you just like to watch?
You say you haven't got the hang of Hypercard yet. You don't think you have anything that would interest other HC users? You say you're still having trouble putting the disk in the right side up. You say you can't download the upgrades (or upload the downgrades) because you're not a telecommunicatin' fool? You say you can't get the upgrades from a users group because you wouldn't want to belong to any group that would have you as a member. No Problem. Have we got a deal for you. For the price of a hamburger you can stay abreast (a breast?) of all the happening events in the Hypercard world. Just send $5.00 (well, a pretty big hamburger) and you will get the latest version of the complete stack (be sure to let me know what version you have). I'll also throw in the latest stacks and public domain software going around. You don't even have to send a disk or a return envelope or anything. Just your name & address, oh, and of course, THE MONEY!!! WHAT A DEAL!
-- part contents for card part 6
----- text -----
Registered Trademark of Apple Computer. (He made me say it, Ma!)
External Function resources, used to extend the usefulness of HC.
-- part contents for card part 8
----- text -----
External Command resources, used to extend the usefulness of HC.
-- part contents for card part 9
----- text -----
Since it is a repository for alot of different types of information on HC, I call it a library. Besides, who wrote this stack, anyway?
-- part contents for card part 10
----- text -----
This is neat. It will automatically copy all the new cards and resources into the right places in the Developers stack with just a click of a button.
-- part contents for card part 11
----- text -----
Registered trademark of Apple Computer. Hey, wait a minute. Angus Macintosh might have something to say about that. (I wonder how that goes over in Scotland -- "Yeah, I just bought a Macintosh").
-- part contents for card part 12
----- text -----
Steve Drazga...
Wait a minute, isn't he the guy that is putting out the Developer stack? What a sport!
-- part contents for card part 13
----- text -----
American dollars or Japanese yen only. None of that Canadian stuff, eh.
-- part contents for card part 14
----- text -----
I'm not talking about the kind of resources you move with resedit. I'm talking about the kind of resources you use to make life easier for yourself. A remote control is this kind of a resource.
-- part contents for card part 15
----- text -----
If lots of people send in their tricks and techniques, it may come out at two week intervals. If everyone sits on their backsides staring at 9 point type on a computer screen like, for example, YOU, then it may come out only once a month or so. The point is, there are lots of people doing lots of Hypercard programming. We just have to get together.
-- part contents for card part 16
----- text -----
"Ha! You bought a Macintosh?! Isn't that cute. It's got a cute little screen. It must be fun to play with. And look at those cute little pictures. I guess you have to be pretty stupid to need little pictures, huh..."
Anybody who was part of the Macintosh front lines, in 1984 and 1985 remembers that. Guess they finally realized that IBM users are just as stupid as Mac users, with PS/2 et al.
-- part contents for card part 17
----- text -----
ART Incorporated is a Macintosh consulting & software development firm located in Moorestown, NJ. For more information on how you can integrate the Macintosh system into your working environment, give us a call at (609) 778-3601.
(CDRM1080320)(1993).iso/FILES/HYP/C-D/DeveloperStax.cpt/Developer Stack 1.0/card_16113_render.png){kind=link}